

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Create Traceability Diagrams [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Traceability,Traceability Diagrams,Diagram,Diagram Traceability">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Create Traceability Diagrams</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="packages_and_elements.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="traceability_tools.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">Having structured the models of a project to indicate directions and theoretical relationships between the models and packages, you can formalize these directions on a </span><span class="f_BodyText" style="font-style: italic;">Traceability</span><span class="f_BodyText"> diagram, using </span><span class="f_BodyText" style="font-style: italic;"><a href="realise.htm">Realize</a></span><span class="f_BodyText">, </span><span class="f_BodyText" style="font-style: italic;"><a href="trace.htm">Trace</a></span><span class="f_BodyText"> and similar relationships.</span></p>
<p class="p_BodyText"><span class="f_BodyText">You initially create a Traceability diagram as a <a href="customdiagram.htm">Custom</a> diagram, but if you are creating the diagram manually you can use elements and relationships from other </span><span class="f_UIControl">Toolbox</span><span class="f_BodyText"> pages to develop the diagram as broadly as is necessary.</span></p>
<p class="p_TextIndentedL2"><img src="traceability%20-%20trace.png" width="782" height="695" border="0" alt="Traceability - Trace"></p>
<p class="p_BodyText"><span class="f_BodyText">You can also generate the diagram using the </span><span class="f_MenuKeyField">Add | Related Elements</span><span class="f_BodyText"> <a href="insertrelatedelements.htm">context menu option</a> to automatically bring in elements linked to the selected element. It is probably better to add the elements in stages, one level at a time, but you could add several levels in one go to see how far the hierarchy extends and to identify relationship and element types to exclude from the 'clean' diagram. You could perform a similar operation, one element at a time, using the <a href="linktab.htm">Relationships window</a>.</span></p>
<p class="p_BodyText"><span class="f_BodyText">The above diagram instantly shows how two levels of Requirements are realized by Use Cases, and which Requirement is realized by which Use Case(s). It also shows how some of the Use Cases are implemented by Class elements. Further, you can drill down on the Use Cases (or, in other Traceability diagrams, any other composite elements) to display more detailed diagrams showing how the Use Case meets the Requirement. The </span><span class="f_BodyText" style="font-style: italic;">Close Account</span><span class="f_BodyText"> Use Case, for example, contains a Communication diagram and a Sequence diagram.</span></p>
<p class="p_BodyText"><span class="f_BodyText">You can tailor your Traceability diagrams to depict any level of granularity and any stages of development that are appropriate. You might narrow the above diagram, for example, to show development from just the </span><span class="f_BodyText" style="font-style: italic;">Remove User</span><span class="f_BodyText"> Requirement, and extend it to include Interfaces, Components, Test Case elements or any other facet of the system or process.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Whilst the Traceability diagram itself provides information on the definition, design and implementation of a business process feature, much more information can be obtained using <a href="traceability_tools.htm">tools</a> such as the </span><span class="f_UIControl">Relationships Matrix</span><span class="f_BodyText"> and relationships </span><span class="f_UIControl">Hierarchy</span><span class="f_BodyText"> window.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
